Method and system for allowing customization of remote data collection in the event of a system error

ABSTRACT

In a computer system, a method and system for allowing customization of data collection in the event of a system error is described. In one embodiment, a Program Registration Table (PRT) contains entries associating a program name with an executable file and associated parameters. Additionally, an Error Matrix (EM) includes entries specifying which program(s) in the PRT to execute in response to a particular system error. In the event of a system error, the program(s) to execute is determined by examining the entries in the EM. The program(s) is then executed. The output from the program(s) executed may then be sent offsite for analysis. Changing the behavior of the machine in the event of a system error may be accomplished by updating entries in the PRT and EM, without the need to change any code on the system.

BACKGROUND OF THE INVENTION

[0001] 1. Technical Field

[0002] The invention relates to computer systems and more particularly to collection of system data, and still more particularly to a method and system for allowing customization of data collection in the event of a system error.

[0003] 2. Description of the Related Art

[0004] The use of computer systems is becoming prevalent in commercial as well as personal arenas. Despite the common use of computer systems, many users are incapable of diagnosing and correcting errors that occur. The problem of diagnosing and correcting system errors is further complicated from the fact that most systems are geographically distant from service technicians.

[0005] Currently there are two methods for capturing data to help diagnose and correct problems when an error occurs on a computer system. The first is accomplished by using static lists indicating which data to collect in the event of an error. The second method is performed by a technician remotely logging in to the troubled system and executing various diagnostic tools. Each of these methods has undesirable consequences.

[0006] If static lists are utilized, there is no way to tailor the list without updating or adding new code. Adding code to a machine that is currently in-use is a risky venture as it may cause a system to become unstable. For a technician to collect data remotely, the technician must be given access to the machine. Providing a technician access creates security issues that are undesirable when working with systems containing sensitive data.

[0007] Therefore, there is a need for a new and improved method and system for allowing customization of data collection in the event of a system error without a technician logging into the system.

SUMMARY OF THE INVENTION

[0008] As will be seen, the foregoing invention satisfies the foregoing needs and accomplishes additional objectives. Briefly described, the present invention provides an improved method and system for allowing customization of data collection in the event of a system error. In contrast to previous systems, the method and system of the present invention allow for flexible data collection without the need to update code on client machine or have a technician log into the system.

[0009] According to one aspect of the present invention, a method and system for allowing customization of data collection in the event of a system error is presented. A Program Registration Table (PRT) contains entries associating a program name with an executable file and associated parameters. Additionally, an Error Matrix (EM) includes entries specifying which program(s) in the PRT to execute in response to a particular system error. In the event of a system error, the program(s) to execute is determined by examining the entries in the EM. The program(s) is then executed. The output from the program(s) executed may then be sent offsite for analysis. Changing the behavior of the machine in the event of a system error may be accomplished by updating entries in the PRT and EM, without the need to change any code on the system.

DESCRIPTION OF THE DRAWINGS

[0010] The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objects and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:

[0011]FIG. 1 is a high level block diagram of an exemplary computer system used in the present invention;

[0012]FIG. 2 is a high level block diagram depicting one implementation of the present invention;

[0013]FIG. 3a is a table layout illustrating one possible format for a Program Registration Table;

[0014]FIG. 3b is a table layout depicting one possible format for an Error Matrix;

[0015]FIG. 4 illustrates a set of steps one embodiment of the invention carries out in response to a system error;

[0016]FIG. 5 is a pseudo-code listing describing one means of implementing a Fire Rules Component;

[0017]FIG. 6 is a pseudo-code listing describing one means of implementing a Program Registration Table Manager; and

[0018]FIG. 7 is a pseudo-code listing describing one means of implementing an Error Matrix Manager.

DESCRIPTION OF THE PREFERRED EMBODIMENT

[0019] Referring now to the drawing figures, in which like numerals indicate like elements or steps throughout the several views, the preferred embodiment of the present invention will be described. In general, the present invention provides for counting the number of delay cycles attributable to a particular level of memory within a hierarchical memory system.

[0020] With reference now to FIG. 1, there is depicted a block diagram of a data processing system in which a preferred embodiment of the present invention may be implemented. Data processing system 100 may be, for example, one of the models of personal computers available from International Business Machines Corporation of Armonk, N.Y. Data processing system 100 includes a central processing unit (CPU) 102, which is connected to a system bus 108. In the exemplary embodiment, data processing system 100 includes a graphics adapter 104 also connected to system bus 108, for providing user interface information to a display 106. Usually, RDM will be used with more Enterprise Class machines such as a Total Storage Virtual Tape Server.

[0021] Also connected to system bus 108 are a system memory 110 and an input/output (I/O) bus bridge 112. I/O bus bridge 112 couples an I/O bus 114 to system bus 108, relaying and/or transforming data transactions from one bus to the other. Peripheral devices such as nonvolatile storage 116, which may be a hard disk drive, and input device 118, which may include a conventional mouse, a trackball, or the like, is connected to I/O bus 114. Network Interface Card 120 allows the system to communicate with computers (not shown) on a Local Area Network (LAN) or Wide Area Network (WAN).

[0022] The exemplary embodiment shown in FIG. 1 is provided solely for the purposes of explaining the invention and those skilled in the art will recognize that numerous variations are possible, both in form and function. For instance, data processing system 100 might also include a compact disk read-only memory (CD-ROM) or digital video disk (DVD) drive, a sound card and audio speakers, and numerous other optional components. All such variations are believed to be within the spirit and scope of the present invention.

[0023] Referring now to FIG. 2, a block diagram of a preferred embodiment of the present invention is illustrated. Program Configuration Database 222 is composed of Program Registration Table (PRT) 202 and Error Matrix (EM) 204. Program Configuration Database 222 stores information indicating which actions to take in response to receiving Error 206. The format of PRT 202 and EM 204 will be described in more detail in conjunction with FIG. 3.

[0024] Remote Data Manager (RDM) 208 contains Fire Rules Component (FRC) 216 for handling systems errors. Further RDM 208 contains Configuration Component 224 utilized for updating Program Configuration Database 222. The use of Configuration Component 224 and Program Database 222 allows for flexible customization of the behavior of RDM 208 without the need for a user to log into the system or without the need to change the code of RDM 208. The components of RDM 208 will be discussed in greater detail in conjunction with FIG. 5, FIG. 6, and FIG. 7.

[0025] In one embodiment of the invention, when RDM 208 receives Error 206 from the system (not depicted), the information about Error 206 is passed to FRC 216. FRC 216 extracts the error type of Error 206 and examines Program Configuration Database 222 to determine which programs to execute in response to Error 206. Specifically, FRC 216 searched Error Matrix 204 to determine which rules (not depicted) match the error type. The rules that match the error type include a field indicating which programs to execute. After determining which rules match, FRC 216 examines PRT 202 for information about the programs that are to be executed.

[0026] After the information about the programs is obtained, FRC 216 executes the programs located in System Programs 212 with the appropriate parameters. The programs are only executed if the limits set by the associated program attributes all pass. In other words, if a registered data collection program has an attribute stating that it cannot be executed if a specific other program is currently running, then that particular data collection program will not be run. This minimizes the impact data collection programs have on the said system function. Additionally, FRC 216 collects Program Output 214 from the programs executed. FRC 216 then transmits the collected output to Technician 210. Technician 210 may be an automated system, a technician, or other destination that may utilize the collected data.

[0027] RMD 208 also receives update messages (not depicted) that are passed to Configuration Component 224. Configuration Component 224 utilizes the update message to modify Program Configuration Database 222. In one embodiment, Configuration Component 224 determines if the update pertains to PRT 202 or EM 204 and passes the information to PRT Manager 218 or EM Manager 220 as appropriate.

[0028] With reference now to FIG. 3, exemplary tables for a PRT and EM are depicted. In a preferred embodiment, PRT contains entries composed of the following fields: program_tag 302, executable_name 304, attribute 306, attrib_value 308, and attrib_executable 310. Program_tag 302 represents a short-form name of a program to execute. Program_tag 302 is utilized to link information between a PRT and an EM. Executable_name 304 contains a string that is utilized to cause a system to execute the program. Attribute 306, attrib_value 308, and attrib_executable store additional information related to the program. The information may include programs which may not be executed concurrently (concurrent_rdm attribute), a limit on the size of the output of a program (output_limit attribute), the number of times a program may be executed within a given time (freq_check attribute), the amount of time which must transpire before a program may be executed again (black_out_period), or any other desired information. The attrib_executable stores a string that is utilized to execute a program that returns a value signifying whether or not the associated registered data collection program is allowed to be executed. This allows flexibility in defining new attribute types that presently are not foreseen, but in the future may arise as being useful to check.

[0029] An EM table contains entries containing rule_tag 312, pre-conditions 314, and results 316. Rule_tag 312 serves as a name for a rule. Pre-conditions 314 indicate an expression which triggers a rule. For example, in the event of a “gen_tape” error the precondition for executing “tape_rule1” is met. Results 316 indicates the short name or names of the programs to be executed when the rule is triggered.

[0030] Those skilled in the art will readily appreciate that the information stored in the Program Registration Table and an Error Matrix described above may be stored in one table distributed over multiple tables. Further, different sets of fields may be employed to provide the same functionality. Such variations are considered to be within the scope and spirit of the present invention.

[0031] Referring now to FIG. 4, a flow chart of a preferred set of steps to handle system errors in the present invention is illustrated. As depicted at step 402, the process begins when a an Error is received by the RDM. The Error contains a type and may contain additional information about the error. Based on the error type, the RDM searches through the Error Matrix to determine which program or programs to execute as illustrated at step 404. A user may specify the RDM execute all programs that match or only the first.

[0032] Once the RDM has determined which program or programs to execute, it examines the Program Registration Table for more information about the program or programs as depicted at step 406. The information includes the location of the executable, parameters to pass when calling the executable, and attributes that must be checked before the program is allowed to be executed. As illustrated at step 408, the RDM causes the selected program or programs to be executed by the system. The programs may be executed sequentially or in parallel, depending on attributes associated with the programs.

[0033] The output of the executed program or programs is collected and sent to a specified location once it becomes available as depicted at 412. The collected output may be sent electronically or by other means including facsimile to a specified location.

[0034] With reference now to FIG. 5, a pseudo-code listing for an exemplary embodiment of the Fire Rules Component (FRC) within the RDM is presented. The FRC receives one or more error messages from a system. Each error messages has an associated type and as in the illustrative embodiment may be represented as simply a type. Additionally, the FRC receives an indicator (firing pattern) specifying if all rules or only the first which matches the error should be executed. The indicator may be stored in a configuration file, specified when initialing the FRC, or by any other means.

[0035] If the firing pattern is for executing only the first match, the FRC extracts the first rule from the Error Matrix that is a match. If a match is found, the results (the programs to execute) of the match are run (assuming all attributes for each said program are such that they allow the execution). Afterwards, the FRC exists successfully.

[0036] When a firing pattern to execute all matches is specified, the FRC proceeds in a similar manner as described above. However, instead of exiting after the first match, the FRC continues to search the Error Matrix for matches until it reaches the end of the table.

[0037] In addition to code presented, the code could include before the FRC exits, instructions to collect the results, if any, of the program or programs executed and transmitted them to a third party.

[0038] Referring now to FIG. 6, a pseudo-code listing for an exemplary embodiment of the Program Registration Table Manager (PRTM) within the RDM is presented. The PRTM allows the behavior of the RDM to be customized after deployment without the need to log into a system or change the code of the RDM. The PRTM may receive messages that originate from different sources. For example, a user of a system may utilize a local configuration tool or offsite personnel may send an electronic message to the PRTM.

[0039] Regardless of the origin of the update message, the update message must contain enough information as to allow the PRTM to perform an update. In an exemplary embodiment, the update message contains data indicating the modification type (add, delete, update), a program tag, an executable name, and attribute fields. The pseudo-code listing in FIG. 6 illustrates a set of steps that may be taken when given the above information to update the PRT.

[0040] With reference now to FIG. 7, a pseudo-code listing for an exemplary embodiment of the Error Matrix Manager (EMM) within the RDM is presented. The EMM allows the behavior of the RDM to be customized after deployment without the need to log into a system or change the code of the RDM. The EMM may receive messages that originate from different sources. For example, a user of a system may utilize a local configuration tool or offsite personnel may send an electronic message to the EMM.

[0041] A preferred format of an update message for an EMM, as used with the pseudo-code of FIG. 7, includes a modification type, a rule tag, data describing preconditions for the rule, and data describing results for the rule. The pseudo-code listing in FIG. 7 illustrates a set of instructions that maybe utilized in conjunction with an update message containing the information described above to perform an EM update.

[0042] The present invention has been described in relation to particular embodiments which are intended in all respects to be illustrative rather than restrictive. Alternative embodiments will become apparent to those skilled in the art to which the present invention pertains without departing from its spirit and scope. For example, while the present invention has been described as receiving a system error, the present invention may be utilized to respond to an system event. The term system error includes within its meaning any system event. Accordingly, the scope of the present invention is defined by the appended claims rather than the foregoing discussion. 

What is claimed is:
 1. A system for allowing customization of data collection in the event of a system error, said system comprising: a program configuration database; means for determining one or more programs to execute in response to said system error, wherein said one or more programs are listed in said program configuration database; and means for executing said one or more programs, wherein said one or more programs may produce a program output.
 2. The system of claim 1, wherein said program configuration database further comprises: a program registration table, comprising one or more program registration table entries; and an error matrix, comprising one or more error matrix entries.
 3. The system of claim 1, said system further comprising: means for transmitting said program output to a remote server.
 4. The system of claim 1, said system further comprising: means for managing said program configuration database.
 5. The system of claim 4, said system further comprising: a data program manager.
 6. The system of claim 4, said system further comprising: an error matrix manager.
 7. The system of claim 2, wherein said program registration table comprises program registration table entries comprising: a program tag field; an executable name field; an attribute field; and an attribute value field.
 8. The system of claim 2, wherein said error matrix comprises error matrix entries comprising: an error tag field; a precondition field; and a result field.
 9. The system of claim 3, said system further comprising: means for receiving an update message, wherein said update message is utilized to update said program configuration database.
 10. A method for allowing customization of data collection in the event of a system error, said method comprising the steps of: determining one or more programs to execute in response to said system error, wherein said one or more programs are listed in a program configuration database; and executing said one or more programs, wherein said one or more programs may produce a program output.
 11. The method of claim 10, wherein said program configuration database further comprises: a program registration table, comprising one or more program registration table entries; and an error matrix, comprising one or more error matrix entries.
 12. The method of claim 10, said method further comprising the step of: transmitting said program output to a remote server.
 13. The method of claim 10, said method further comprising the step of: managing said program configuration database with a data program manager.
 14. The method of claim 11, wherein said program registration table comprises program registration table entries comprising: a program tag field; an executable name field; an attribute field; and an attribute value field.
 15. The system of claim 11, wherein said error matrix comprises error matrix entries comprising: an error tag field; a precondition field; and a result field.
 16. The method of claim 12, said method further comprising the step of: receiving an update message, wherein said update message is utilized to update said program configuration database.
 17. A computer usable medium for allowing customization of data collection in the event of a system error, said computer usable medium comprising: computer program code for determining one or more programs to execute in response to said system error, wherein said one or more programs are listed in a program configuration database; and computer program code for executing said one or more programs, wherein said one or more programs may produce a program output.
 18. The computer usable medium of claim 17, wherein said program configuration database further comprises: a program registration table, comprising one or more program registration table entries; and an error matrix, comprising one or more error matrix entries.
 19. The computer usable medium of claim 17, said computer usable medium further comprising: computer program code for transmitting said program output to a remote server.
 20. The computer usable medium of claim 17, said computer usable medium further comprising: computer program code for managing said program configuration database with a data program manager.
 21. The computer usable medium of claim 18, wherein said program registration table comprises program registration table entries comprising: a program tag field; an executable name field; an attribute field; and an attribute value field. 